I want to upgrade to Aptana 3, but on first glance there were a few things different I didn't have time to spend figuring them all out. So I went back to 2. I'd like to install 3 as well so when I have time I can just look at it. I use Aptana too much and rarely have a lot of time to spending figuring out all their changes but there are some benefits to upgrading.
So is there a way I can hide my Aptana 2 from the install wizard for 3?
While it's not quite what you asked for, I would install the 3.x version as a plugin into Eclipse. Realistically, you should be able to install 2.x and 3.x side-by-side, so the fact you can't sounds like a bug, and I would recommend filing a bug ticket for that.
Related
Although I have a good understanding of NPM and bower to include packages in web projects, I would expect from meteor, which has a very own packaging logic, that core packages are kept up to date?
Meteor = make things easy, right? I struggled for a few hours, why meteor was not recognizing col-md-6 until I figured out it doesn't have version 3.
No it has version 3 , you can add that package using
meteor add mizzao:bootstrap-3
from meteor 0.9 version and above for more check here
(https://github.com/mangasocial/meteor-bootstrap-3)!
Meteor shipped with several packages as "core" when it was still pre-1.0. That was when no useful packaging system was available, so the folks behind Meteor were kind enough to get developers a quick start with providing several packages.
Now that we are post 1.0 they have decided to focus their energy on developing Meteor, and not bringing in packages that can easily maintained by the community. The packaging system is available and well documented so that MDG can refrain from shipping (and maintaining!) packages that are not essential for the Meteor platform.
While I personally would have liked to see each and every package I'd need in my projects to be part of the officially maintained core, it is simply not feasible. To avoid confusion, the bootstrap package is about to vanish from meteor core soon, as you can see from the History.md for the next version
Some packages are no longer released as part of the core release process: amplify, backbone, bootstrap, d3, jquery-history, and jquery-layout.
You've to have in consideration that Twitter (the company in charge of the project) isn't the official owner of the package in Atmosphere, It's a community package and if you don't like: you don't use it. That's pretty much how it works, I've had my dose of problems with atmosphere packages, now: I simply read most of the code before using a package. You can easily spot obvious mistakes/behaviours just by reading some lines.
I have to upgrade website running very old version of Drupal (cannot even find out which version is that, but I guess it is even before 5) to the newest one? Is that possible? If yes, how to approach this?
The Drupal web site makes it clear that you cannot skip major versions when doing version upgrades.
See this page: http://drupal.org/upgrade/
(it talks about not being able to skip from v5 to v7; it doesn't even mention v4!)
So if you do manage to upgrade your site all the way from v4.x to v7, one thing is for certain - it's going to be a long-winded process.
The other thing that is going to be a major issue for you is that the Drupal module ecosystem has changed radically in the space of time between v4.x and v7. Many modules that you'll be using in v4 will be either unsupported in later versions, or not have an upgrade path, so you may have a lot of manual hacking to do.
On the flip side, there are likely to be newer modules that can do things in recent versions of Drupal which were not possible in older version or were done in a very different way, and you may find yourself wanting to use some of those modules instead of ones you've got in place. Again, lots of manual work I forsee for you.
In summary, I would suggest that upgrading from such a long way back to the current version is going to be extremely difficult. You may find it easier to start again from scratch and rebuild everything. I'm sure you could get some data imported from the old site to maintain continuity.
One further thing I would add is that this isn't a Drupal-specific problem, so please don't blame the Drupal developers if you struggle with this upgrade - you'll get this issue with virtually any software you run if you don't keep it up-to-date. Try upgrading a Windows95 machine to Windows Vista and you'll see what I mean.
It would be possible, but could be very hard.
You would need to go from 4 to 5, then 5 to 6, and finally 6 to 7. You will have to make sure that your data is still intact along each upgrade and back up your database. Update any contributed modules and check if any have been deprecated along the way and find suitable replacements if possible.
Depending on your site, if it is just the content and you are not concerned with losing url aliases, taxonomy terms, etc. then trying to export/import your raw data directly into a fresh drupal 7 install might be easier.
Edit: You would also need to upgrade any custom themes and modules drastically.
I do not envy your task, as you will need to learn the changes from D4 to D5 only to later discard this knowledge as you learn the changes to become D6 compatible and then discard that knowledge to become D7 compatible.
As you said you do not really care about losing taxonomy terms or extras, you might want to try http://drupal.org/project/import_html or a similar module to scrape your website (though it is not actually static) and convert it automagically into nodes. That module is not currently available in D7, but would get you from D4 to D6.
The key thing to remember is frequently backup your database in case anything goes wrong or you want to try different upgrade paths.
It is doubtful that many contributed modules you are using would survive the upgrade, unless there is a release for each of versions 4, 5, 6, and 7. I agree with #brian_d, the best course of action may be to export your content and import into a fresh Drupal 7 site.
The general procedure for updating:
Assuming you are on version 4.7.x of Drupal:
Update Drupal and any contributed modules you can to the latest release for 4.7.x, in case there were schema changes
Disable contributed modules
Update Drupal to the latest version of 5.x
Update and re-enable modules/themes to the latest release for 5.x
Repeat steps 2-4 for 5.x to 6.x and again for 6.x to 7.x
I've been using Drupal since 4.x. During that time I've had to upgrade numerous times. Mostly I've had good success using the standard upgrade process. However, I've had to do several upgrades manually because of one issue or another. This was basically a Copy and Paste upgrade.
To read more about the Copy and Paste Upgrade go here: Upgrading Drupal by Copy and Paste.
Any issues? Does it replace 3.2? Appreciate the help/insight.
As long as Xcode 4 is a developer preview instead of a supported release, you are taking a big risk if you depend on Xcode for your livelihood. If you are interested only in hobby work, then the only thing you have to loose is a little hair (yes, there are several outstanding issues in preview 3). Once Xcode 4 is released, I think it provides many compelling features and I will happily move my development efforts over to the new version. Unlike Windows/Visual Studio, Xcode releases are not tied to operating system or library versions, and the Xcode team has made it so that versions 3 and 4 play very well together. So you can use either Xcode 3.x or Xcode 4 interchangeably.
Plain and simple: Because it's a Developer Preview! :)
(and personally: still crashes a lot on my machine)
And correct me if I'm wrong, but XCode4 still lacks several features.
Some basic features are also still not working as expected. When you write for Code Sense will suggest a long list for keywords. But the for-loop is still missing from the list. I am sure we all know how to write such a loop but for a beginner it still would be useful as it is in Xcode 3.2
I've found XCode 4 to be stable enough for daily work as of the DP5 release, and Apple is actually encouraging this now.
When (and you will) you run across things that don't work, or XCode crashes, just switch back to XCode 3.2 and work past the issue. The project file format is compatible so this isn't an issue at all.
Overall, XCode 4 is shaping up to be an awesome tool.
If you have a Core 2 Duo or earlier, DO NOT UPGRADE. Xcode 4 is a great tool with many wonderful additions, but slower Mac's can't handle it. You'll often find yourself typing then waiting for the editor to catch up.
I'm trying to find 1, just 1, working sample project for Red5 that's updated to work against the latest 0.9 release without missing jars and other nonsense.
Right now, it's at v0.9 and the libs are different from other versions. They have 5 pathetic examples on their website, but all were built with the older versions. For these 5 old examples, I could use the Add External JARS feature to try and add libs from previous versions, they don't mention which versions they were built against and I'm not going to try each previous version to see which works (I already did and nothing works). They don't seem to be putting any effort into updating or marketing their open source project.
Anyone who's more intelligent and can shed some light on behalf of these fools?
What sorts of issues are you having? What sorts of projects are you trying to build?
I'm by no means an expert on this - and I admit that the lack of documentation is pretty frustrating.
However, I just downloaded their latest, installed it and got the olfa demo running pretty seamlessly.
The source for the demos are available here, and I use these to work out what I need.
http://www.smartfoxserver.com/ makes use of red5 in someway. Perhaps you can find something useful in their (well documented) examples, good luck.
I'm planning to install Drupal. Is there any reason not to install the latest 6.x version as opposed to the 5.x branch? Are there any really good modules that are 5.x only?
Unless you have a 5.x module that you can't do without, and that you know is being worked on to upgrade to 6.x, just use 6.x. i.e. Only start with 5.x now if you know you have a upgrade path with your site to 6.x (and then 7.x). If the module isn't being actively worked on, it mean you'll be unsupported when 7.x rolls around, so you might as well solve the problem of doing without that module with 6.x now rather than wait till your site is developed and up and running.
I've found enough modules to happily run my site on Drupal 6.x I think the only 5.x module I miss is one that did very easy Google ad integration, and that may have been updated I just haven't checked recently. I don't get enough traffic to make the ads worth the time in setting them up, so I just use the search part of the ad campaign.
Drupal 7.x is under development now, so I would expect that anything that hasn't been moved from 5.x to 6.x is just not being developed anymore, and is probably not really that needed.
Ultimately, take a look at what modules you may need. With an account on Drupal's site, you can filter by install type. I found that 6.x is much easier to work with in some regards (managing and upgrading modules) and overall I've had a much easier time maintaining my site under Drupal 6.x than I did under 4.x or 5.x.
I also think that 6.x runs much faster.
My bosses were insistent on making Drupal 6 sites for clients as soon as it was released. This was a headache, because views and CCK were not done, as well as many other modules. Their rational was that we'd have to eventually upgrade to 6, and we wouldn't want to go back and redo these sites. It ended up that we had so many workarounds while using the development versions of modules that it was a pain every time we upgraded modules or core itself.
Thankfully, this is no longer the case. Views, CCK, and most other modules are now ready and stable for 6. The only module we use that hasn't been upgraded is eCommerce, and it doesn't look like it will be, since ubercart is pretty much the Drupal standard for commerce functionality.
We asked ourselves the same question several months ago (just before Drupal 6 was finalized & released)
Our office has limited development resources, and we had released a couple of D5 sites, and a D5 sales app.
We went with Drupal 6.
The decision came after considering the core of what we were interacting with. CCK & Views are the only die-hard critical components for anything besides a default Drupal install, and the level of participation and vitality of the projects was very encouraging.
The stuff that really, really matters, has been/is being ported over to D6, and the wow, this would be nice, p2 stuff is hit & miss.
If you're doing any module development, D6 is a winner.
If you're already very comfortable with D5, then stick with it.
I hope this helps.
The one significant CCK-related module that's not D6 production ready is filefield. This may not be an issue if you're not doing anything substantial with images and media, but might be worth considering if you're going to do any serious DAM. Otherwise, I think we're (finally!) to the point where it's making more sense to go with D6 than D5. Either way, it's definitely worth the time to architect the site according to your specific needs, figure out what modules you'll need and find out if any of them have yet to be updated.
The asset module is not available for D6 yet, not even in a development branch. I've heard a lot about its benefits as a single way to manage all kinds of media files, but most sites can probably happily do without it.
If you haven't been running Drupal before you could find that version 6 has the modules you need. Besides, modules gets ported and created every day so your missing modules could very well be on the way.
For me, the lack of a protx payment module was a deal breaker when choosing which version to use.
The best thing to do is get a full list of requirements before you start, and make sure it's all available in 6.
As a module developer, I feel that Drupal 6's API is more mature then version 5.
So even if you decide to choose 6, and then finds a module is missing, it will be easy to develop it to 6.
Now that I've used Views 2, I ain't ever going back (unless it's to revisit old projects).
I think now, all modules and themes that are of any worth have been migrated and now I'm seeing a trend of new (actually good themes) are drupal 6 only as are quite a few of the must have modules.