I'm currently working on the next release of base2. It was going to be
version 1.1 but this bug:
http://code.google.com/p/base2/issues/detail?id=126
makes me think that I need more than a point release.
A change to the packaging system is pretty fundamental. The new system
is not backwardly compatible with the old system and for this reason I
think that base2 should move to version 2.0.
There is also a new feature base2.require() that allows lazy-loading of
base2 packages and other 3rd party scripts. With the next release, I
will also release the other packages:
* base2.jsb (JavaScript beaviors)
* base2.io
* base2.jst (JavaScript templates)
What do you guys think? Should the next release be version 2.0 or
version 1.1?
Other Changes
=============
1. I also want to get rid of the "JavaScript" namespace. Array2 etc will
now live on the base2 package:
var myArray = new base2.Array2(1, 2, 3);
2. I also want to move to lowercase package names:
base2.DOM -> base2.dom;
I will provide backward compatibility for the above changes in a 1.1
release but won't bother if we move to 2.0.
Let me know your thoughts. I don't want to make changes for the sake of
it and I don't want to upset current users.
Moving to version 2.0 gives me a chance to rebrand base2 and hopefully
gather new interest in the project.
-dean
> What do you guys think? Should the next release be version 2.0 or
> version 1.1?
+1 for 2.0 too.
- benoît
And jsb is also welcomed to be in the release.
Although I also found a way to refer to a specific version in
subversion trunk:
http://base2.googlecode.com/svn-history/r283/trunk/lib/base2-jsb-fp.js
+1 for 2.0.
--
Best wishes, Alexey Simonenko
Chief developer, «Serenity Ltd»
Office phone: (812) 448-55-12
Mobile phone: (812) 923-95-74
http://www.google.com/profiles/dwarfman
While we're talking about changes I've got one I'd like to ask about.
Have you thought about moving away from SVN? I read how google added
Mecurial support to google code. I haven't used Mercurial but from
what I understand it could facilitate more collaboration on the code
(anyone can make their own branch).
-- m
http://mercurial.selenic.com/wiki/WorkingWithSubversion
I think subversion lowers the entry barrier for base2; and that's a
good thing.
These are my two cents...
I'm very interested in that. I've got base2js.com but really I lack content.
JSB has good documentation:
And the API viewer is getting better:
http://base2.googlecode.com/svn/doc/base2.html
But I need some examples and tutorials to make the site useful.
> While we're talking about changes I've got one I'd like to ask about.
> Have you thought about moving away from SVN? I read how google added
> Mecurial support to google code. I haven't used Mercurial but from
> what I understand it could facilitate more collaboration on the code
> (anyone can make their own branch).
I have considered it. The thing is, SVN is up and working and I don't
really have time to look into it. If you want to help in that area then
I will certainly entertain the idea.
I'm quite keen to build more of a community around base2. I've continued
to develop and support it. And I've been able to build good things on
top of base2 which prove its worth. I guess I'm not the charismatic
leader type. :)
-dean
I'll get to posting some logo concepts soon.
--
m
I look at the scope of the project as pretty huge for what is
basically a solo act. Don't be too hard on yourself :) As for building
a community I'm not sure my suggestion change to a dvcs would help.
Though speaking of that I was experimenting with Bazaar and the
launchpad.net platform. I pulled in base2 as a project there. So one
can use a different version control system on top of SVN for sure. I
just don't know how useful it is if I ever produce changes that base2
would like to pull in. See base2 in launchpad at:
http://launchpad.net/base2
I hope you don't mind Dean. I was interested in exploring the
launchpad system not suggesting a change to it or anything. There is a
logo concept that I uploaded there. Take it as a draft the finishing
is probably not right.
--
m
--
You received this message because you are subscribed to the Google Groups "base2-js" group.
To post to this group, send an email to base...@googlegroups.com.
To unsubscribe from this group, send email to base2-js+u...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/base2-js?hl=en-GB.
Nope. They only offer a SVN importing service. They use Bazaar (like
git, yet another dvcs)
http://bazaar.canonical.com
base2 and base2.dom are pretty much complete and I probably won't be
adding much functionality to those libs.
I initially built base2/base2.dom as a platform to build the html5
support library. JSB is an important part of that exercise too. I'm not
particularly attached to the other packages (JST, IO, etc). But they
seem to work well enough so I'm happy to support them.
The only area where I'm developing new stuff is for HTML5-now and to a
lesser degree, JSB.
> Though speaking of that I was experimenting with Bazaar and the
> launchpad.net platform. I pulled in base2 as a project there. So one
> can use a different version control system on top of SVN for sure. I
> just don't know how useful it is if I ever produce changes that base2
> would like to pull in. See base2 in launchpad at:
> http://launchpad.net/base2
> I hope you don't mind Dean. I was interested in exploring the
> launchpad system not suggesting a change to it or anything. There is a
> logo concept that I uploaded there. Take it as a draft the finishing
> is probably not right.
I don't have a problem with you setting this up. I'm not at all familiar
with launchpad so I'll have a look at it. But really, I'm happy to go
along with others on this.
I couldn't see the logo. Is it the blue thingy in the top left?
-dean
It is the blue thingy in the top left. But don't worry about that now
since I've made some pages to present the design concepts I have so
far:
http://groups.google.com/group/base2-js/web
Take them as drafts. We can polish them up if you are interested in
any of them. As I hope you'll agree I've gone for simple and strong.
I've not really delved into the typography too much yet and have
focused on a symbol for now. I've released the designs with a
derivatives-allowed license because it seems like the identity for an
open source project ought to be open as well.
That's it for now. Leave comments or questions on the pages if you
please.
--
m