As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
I'm looking for an existing datamap and/or MySQL script that can migrate data between TYPO3 and Joomla. Obviously, both CMS use MySQL and that's great, but I'm wondering if there is already a document/script that takes the elements from TYPO3 database and puts them in the Joomla database.
I'm planning to write my own migration program in C# so if anyone has some code snippets for that, it would also be helpful.
Forget that, there are too many differences to make it possible... TYPO3 instances are built typically with many various extension + pages + content elements etc. Although Joomla's initial structure is quite simple (as far as I remember) when you are adding new plugins it changes in many different ways. Conclusion is simple if somebody wrote such 'mapper' between his TYPO3 and his Joomla most probably will not work in any other combination.
How many pages are there in the TYPO3 ? if less than 100 I wouldn't waste a time for any programm, just copy/paste it in common editing mode.
If more, I think that would be best solution to write a TYPO3 extension (PHP), which will get all required data from some page using it's parsers, configs etc and will convert it to JSON (or even pure SQL insert statements) with structure understandable in Joomla. Keep in mind that many elements can be quite different in the database - than on the client's side. The best example are internal links which in DB are saved just as ID's of pages to which they are pointing. You need to resolve it on the TYPO3 side, or you'll need to learn how relations are built in TYPO3's database to do the same task in your C# application.
Related
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
I work at a small startup as a Data Scientist, and I'm looking for ways to make my analysis a bit more visible/useful to the organization. I'd like to be able to put up a simple web service which allows internal users to run my scripts remotely. They should be able to input a few parameters via a very simple UI, and they should have the option to have the results appear in the browser window (after a possibly long wait), or have them emailed. Results may be a few pdf figures, and they may be Excel spreadsheets (maybe more exotic in the future, but this is it for now).
The scripts are going to be all in Python, which will handle the analysis.
So, I'd like to know what the pros and cons are of using C#/WCF vs. something like Django or Python. I have significant experience in C# working in the Client-side code base here, but I have much less experience with WCF. All of my analysis work is done in Python (and R, to a lesser extent). The main goal is to not take all of my time building a fancy web service/UI---the front end just has to be friendly enough to not intimidate the marketing people. I don't have to worry about encryption, the server will be behind our firewall. I'm pretty platform agnostic, but I think the servers are all Windows based, if this helps.
Thanks in advance.
For extra credit, how does your answer change if some of my scripts are in F#?
You might consider using the Django web framework. You could set up a small app with your python scripts as different views. https://www.djangoproject.com/
And if you don't want to put that much effort into creating a friendly UI you could use twitter bootstrap. http://twitter.github.com/bootstrap/
Then just run the app internally to gather and display data either via HTTP GETs or via e-mail.
edit: I'm sorry I did not read carefully "pros and cons are of using C#/WCF vs. something like Django". I recently made a Django app and it was fairly straight forward.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
Recently i read an article which said something similar to "stop using classic approach in web development where server gets data from any datastore and renders the views to browser. server must only retreive needed data end response it via json or whatever so client can render it as he wants". Obviously this approach decreases network traffic + page load would be faster. But on the other hand we have to write more JS code(like Knockout). What's your opinion? What problems can appear in this case?
The advice is valid, but should be less dogmatic. The reason to switch to a data-fetching approach is pretty simple in reality: it allows you to reuse the calls elsewhere, if you have multiple parts of an application requiring the same data. Depending on how you do it, though, you might run into increased bandwidth usage due to not being able to get exactly the data you want in one AJAX call (thus duplicating/splitting requests).
The other obvious advantage is it allows you to roll out an outside API pretty easily once that is done.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
I'm currently working on a todolist system that acts like a calendar to store your Tasks and can check them off once you are done with it. We should also be able to undo our changes made.
Currently, my project mate is suggesting that we store the data into files with different dates and when we want to search for a particular task, just search whether the file exists, then edit and directly manipulate the files when needed.
However, I feel that it is better to store the data into 1 large file and load it into memory(possibly a list of tasks) when our program is executed. I can't explain why though.
Does OOP come into the picture when dealing with this?
Sorry if I am a bit confused as I am still learning.
It is a perfect task for a database solution. I suggest that you use the SQL server database that was included with your Visual Studio for this task.
Store each task as rows in a table and select dates and subjects for the calendar view and all the values of one task when editing. VS has some pretty good tools to create such an application in a few minutes (for an experienced user)
Handling files is always a mess when several persons need to edit the data at the same time.
Always the best practice depends on your work you are doing as for todo list you have to make multiple operation on ,
So its going to better if you use client side memory like a sdf file to do this instead of making files because sdf file will work as database and because its an light weight with large data to so easy to handle than file
Firstly this is a persistence problem and should be dome using well known patterns. You could use a database and repository pattern to solve this. Nosql database are also an option ,as thy are easy to setup and lacks the overheads associated with SQL dbs.
But if flat files is your option then holding all data in memory has the flaw of when an exception occurs or the program shut you loose all you data. Persistence is necessary using create read update ans delete CRUD cycles.
This results in persisting in small chunks as you go and you only loose a small amount of data if you crash.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 10 years ago.
I'm looking for a way to easily read in a C# file and place it into a Java Object for database storage (storing the class name, functions, variables, etc).
I'm making a Hierarchical State Machine AI Building Tool for a game I'm creating and need to be able to import an existing C# file and store it in a database for retrieval in the future.
Does anyone know of any preexisting libraries for parsing C# files? Something similar to JavaParser?
Thanks everyone!
EDIT: This needs to be part of my Java Project. I'll be loading in the C# files through my Java Application and saving it into my db4o database.
You could use Roslyn, but it would be a bit of work: http://msdn.microsoft.com/en-US/roslyn
Roslyn is only in Preview, by the way. Microsoft hasn't said when the actual release will be out.
This is a C# library. You will need to do the actual parsing with a C# program using Roslyn.
This page talks about an IL to Java byte code compiler called grasshopper, but it doesn't seem to be there anymore. Maybe you could have done that and use reflection after loading the compilates, not sure where that leaves the code itself, if you need that as well.
As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.
Closed 9 years ago.
I am a beginner to .Net. Recently I am working on a small practice project in which i want to interact with SQL DB using Datasets in VS .net 2008. Kindly suggest me few readings regarding Typed Datasets.
If you prefer to work with datasets (and ado.net in general), I would recommend Microsoft ADO.Net Core Reference. The book is dated now, but in my opinion, so is using datasets. Either way, you can't beat that book in my opinion. The follow up book, which covers ADO.Net 2.0 is more modern and done almost as well as the original (though the original will teach you more about how everything works).
you can google these things. however check the below links
MSDN Documents
Creation of Typed DataSet
A search in google for DataSet Examples C# turned the following results:
DataSet examples C#
Are you sure you want to use DataSet? There are a better techniques now for accessing and manipulating data.
Update:
Depending on your needs there are other ways to access data.
If you need speed - you will probably need to use SqlDataReader.
If you need ease of use, you may skip the more "core" ways of accessing data and use Entity Framework.
Retrieving data with Sql Data Reader
Getting started with Entity Framework
The difference is that SQL Data Reader is the most native way of accessing data. It it uses something like cursor you iterate over.
Entity Framework on the other hand is a fully featured OR/M solution for Microsoft Visual Studio, you basically tell Visual Studio where your data is and it will generate the data classes for you. From there - you just use those classes. It is really easy to use but it uses reflection under the hood which makes it a bit slower than the Sql Data Reader.
Hope this helps!