Sorry - I guess I sounded pessimistic on my previous post.
After closer look - it seems only those two iterators e.g 
BreadthFirstIterator, DepthFirstIterator - use Deque. and ArrayDeque. The 
other iterators work fine.

So I would really appreciate any help with porting them to GWT ??

Would still like to know more about *com.google.gwt.dev.jjs.impl.gflow.Graph, 
though :)

*

On Saturday, September 14, 2013 7:31:51 PM UTC-4, [email protected] wrote:
>
> Hi Jens,
>
> Seems to be more problem than anticipated.
>
> Some of the graphIterators e.g BreadthFirstIterator, DepthFirstIterator, 
> use java.util.ArrayDeque & java.util.Deque. Without the iterators, I will 
> have to roll-out my own traversal mechanism - which seem counter-intuitive 
> of using the (jgrapht) library.
>  - so maybe I will drop down to some other libraries.
>
> Curious about the following questions which i posted in my first post of 
> this thread.
> *
> Finally I stumbled across "com.google.gwt.dev.jjs.impl.gflow.Graph" 
> inside gwt-dev.jar. - But I couldn't find any documentation related to it 
>
> Is it possible to use this to create my own Graph data structure. ? Is 
> there any hints/documentation that I could use.
>
> And related question  is what is gflow - is it for gwt compilation flow 
> usage?  or can this be used for creating flows in our own application too??
> *
> - any ideas on this?
>
> Regards
>
> On Thursday, September 12, 2013 9:35:13 PM UTC-4, [email protected] wrote:
>>
>> Hi Jens,
>>
>> Thanks a lot. 
>> That worked - infact, I had already extracted the classes I needed into 
>> my own project, instead of building with the external jgrapht lib. So i 
>> didn't really have to go the super-source version.
>> However, your response prompted me to look up what exactly is 
>> super-source and hence learnt something new.
>>
>>
>>
>> On Thursday, September 12, 2013 6:06:36 PM UTC-4, Jens wrote:
>>>
>>> Seems like the GitHub search is not correct.
>>>
>>> I don't have the source checked out so I can't do reference searches, 
>>> but it seems like that ClassBasedEdgeFactory is used by all the different 
>>> Graph types if you provide a class for the edge in a constructor. But these 
>>> Graph classes all have a second constructor taking an EdgeFactory. So you 
>>> could create a super source version of ClassBasedEdgeFactory that just 
>>> returns null and never use the class based constructors.
>>>
>>> In your GWT code you would then use something like
>>>
>>> new SimpleGraph<String, DefaultEdge>(new EdgeFactory<DefaultEdge>() {
>>>   DefaultEdge createEdge(String source, String target) {
>>>      return new DefaultEdge(); 
>>>    }
>>> }
>>>
>>>
>>>
>>> -- J.
>>>
>>>

-- 
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to