Hi Worth,

we are definitely interested in a pull request (or multiple if it makes sense 
to split up the functionality).

Keep us posted. TIA.

Best regards,
Bart

-- 
Bart van den Eijnden
OpenGeo - http://opengeo.org
Expert service straight from the developers.



On Jun 26, 2013, at 5:31 PM, Worth Lutz <w...@mindspring.com> wrote:

> Greetings,
>  
> I’ve tried to use GeoExt2 on an ExtJS project of mine.  I had some problems 
> and had to write some of my own components using GeoExt2 as an example.
>  
> Here is a brief description of my problems.
>  
> OpenLayers objects require instantiated objects in their configuration 
> objects. This does not fit in with the new ExtJS4 architecture.  I did not 
> want to instantiate my map with specific code in the launch function.
>  
> I have created a map component which can receive a JSON configuration from 
> the server. I have this working for a limited part of OpenLayers (the parts I 
> need J).
>  
> I create my applications using Sencha Architect. I can include GeoExt2 type 
> components that I created in the project now.  I do not have to build a map 
> in the launch method or instantiate all the layers in the map there. Layer 
> definitions come in the JSON configuration for the map or have there own. 
> Same for other OpenLayers objects. I can change the JSON definition of the 
> map and my application changes without modification.
>  
> Using techniques demonstrated in GeoExt2, I have other control components 
> which can be bound to one of the maps in the application.
>  
> After I finish my current project, I should have some time to put together 
> some examples to go with my code and submit a pull request if you are 
> interested.
>  
> Worth Lutz
>  
> From: dev-boun...@geoext.org [mailto:dev-boun...@geoext.org] On Behalf Of 
> Bart van den Eijnden
> Sent: Wednesday, June 26, 2013 10:14 AM
> To: Marc Jansen
> Cc: GeoExt Dev
> Subject: Re: [Dev] Next steps towards GeoExt 2
>  
> Hey Marc,
>  
> trying to reboot this, any plans to work on a GeoExt 2 release before FOSS4G?
>  
> Latest is now Ext 4.2.1.
>  
> Best regards,
> Bart
>  
> -- 
> Bart van den Eijnden
> OpenGeo - http://opengeo.org
> Expert service straight from the developers.
>  
>  
>  
> On Oct 16, 2012, at 9:10 AM, Marc Jansen <jan...@terrestris.de> wrote:
> 
> 
> Hi Eric,
> 
> thanks for the comments. Good I can count you and Bart in :-)
> 
> Regards,
> Marc
> 
> 
> On 12.10.2012 11:19, Eric Lemoine wrote:
> 
> On Wed, Oct 10, 2012 at 9:18 AM, Marc Jansen <jan...@terrestris.de> wrote:
> 
> Hi all,
> 
> Hi Marc
> 
> 
> 
> I personally feel that GeoExt2 is basically ready for prime time. We used it
> successfully in some fairtly big applications and only found minor
> bugs/annoyments we already fixed in the codebase. There is still at least
> one fixed bug I am going to integrate into the master-branch soon.
> 
> Nevertheless, I suggest to start the release process for the version 2 of
> GeoExt.
> 
> Do you share that opinion?
> 
> Yes. I was thinking about an alpha release, or 0.1.
> 
> 
> 
> I think that there is still a lot of work, though:
> 
> We should double check all classes and examples with regard to
> 
> API compatibility with v. 1
> documentation
> tests
> and some sort of coding style
> 
> Where will we be hosting the API docs? Are we going to change geoext.org? Or
> shall we simply stick with gh-pages? Are we going to integrate runnable
> examples inside of the documentation?
> 
> For an alpha release I'd go with gh-pages for the API docs. We could
> also use gh-pages for hosting the examples and the test runner.
> 
> 
> 
> We also need some prose docs / tutorials
> about migrating existing application
> building a single-file application
> getting the best out of MVC
> API-changes (If we have any)
> 
> What is the release procedure? Are the steps outlined here
> (http://trac.geoext.org/wiki/Release/Procedure) still relevant?
> 
> With the GeoExt project now using GitHub this procedure should be updated.
> 
> 
> I suggest starting with an early beta version in the next few days, so that
> we can make people aware of GeoExt2 and hopefully get feedback about the
> library.
> 
> I do think we should start with that.
> 
> 
> 
> In case you agree with the starting of the release process, we also need to
> decide who will be the release manager?
> 
> Go for it :) I'll help as much as I can.
> 
> 
> 
> What other points / aspects did I miss?
> 
> Please tell me your opinions and about the next steps needed to get to
> GeoExt 2.0-beta.
> +1
> 
> 
> 
> Thanks a lot Marc!
> 
> 
> 
> 
> 
> -- 
> 
>   Dipl.-Geogr. Marc Jansen
>   — Anwendungsentwickler —
> 
>   terrestris GmbH & Co. KG
>   Pützchens Chaussee 56
>   53227 Bonn
> 
>   Tel:   +49 (0)228 / 96 28 99 -53
>   Fax:   +49 (0)228 / 96 28 99 -57
> 
>   Email: jan...@terrestris.de
>   Web:   http://www.terrestris.de
> 
>   Amtsgericht Bonn, HRA 6835, Komplementärin: terrestris Verwaltungs-
>   gesellschaft mbH, vertreten durch: Hinrich Paulsen, Till Adams
> 
> _______________________________________________
> Dev mailing list
> Dev@geoext.org
> http://www.geoext.org/cgi-bin/mailman/listinfo/dev
>  
> No virus found in this message.
> Checked by AVG - www.avg.com
> Version: 2013.0.3345 / Virus Database: 3199/6440 - Release Date: 06/25/13

_______________________________________________
Dev mailing list
Dev@geoext.org
http://www.geoext.org/cgi-bin/mailman/listinfo/dev

Reply via email to