hypertopic / porphyry Goto Github PK

• Scénarios ( Leo Schneider @leoschneider, Valentin Porcelini @Sallaa, Jianwei Zheng)
• Maquettes (Aurore Thomas @aurorethomas, Audrey Henriette @Audreyhrtt, David Galante @folowbaka)
• Tests automatisés (Corentin Laithier @corentinlthr )
• Implémentation (Florent Pergoud @flopshoubox)

as easily as in an outliner

• Scénarios (Jie JI)
• Maquettes (Ruolin ZHENG)
• Tests automatisés
• Implémentation

This feature was already implemented in v5.

• Scénarios (Meng Ruolin Fangxu)
• Maquettes (David Lorraine Yuanjia)
• Tests automatisés (Jie)
• Implémentation (Ruolin Fangxu)

• Scénarios (Meng Ruolin Fangxu)
• Maquettes (David Lorraine Yuanjia)
• Tests automatisés (Ruolin Fangxu)
• Implémentation(Yuanjia)

• Scénarios (Valentin Porcellini @Sallaa , Léo Schneider @leoschneider)
• Maquettes (Aurore Thomas @aurorethomas, Audrey Henriette @Audreyhrtt)
• Tests automatisés (Corentin Laithier @corentinlthr)
• Implémentation (Florent Pergoud @flopshoubox)

This feature was already implemented in v5.

• Scénarios ( Leo Schneider @leoschneider, Valentin Porcellini @Sallaa)
• Maquettes (Aurore Thomas @aurorethomas, Audrey Henriette @Audreyhrtt, David Galante @folowbaka)
• Tests automatisés (Corentin Laithier @corentinlthr)
• Implémentation (Florent Pergoud @flopshoubox)

• Scénarios
• Maquette
• Tests automatisés
• Implémentation

as easily as in an outliner.

Occurred on "stain glasses" Steatite corpora.
Loading related viewpoints caused older "Jonathan's Bookmark" items to be loaded and processed by ItemSet.

Description

What is the valuable outcome that cannot be achieved with current features?

For which stakeholder (people, role, project, domain) is it important?

Which user action should be enabled (or restricted)? For who?

Additional details (solutions you think about, or workarounds you tried)

Deliverables status

Phase 1

• Scenarios (Gherkin)
• Mockups
• Implementation strategy

Phase 2

• Acceptance tests (Capybara)
• Implementation

Phase 3

• Screencast

... since it is now handled by LaSuli.

This feature had disappeared from v5 due to a regression.

... especially on clicking on topics and tabs.

... since LaSuli is a Firefox extension.

This feature already existed in Porphyry v5.

• Scénarios (Fangxu)
• Maquettes (Yuanjia)
• Tests automatisés
• Implémentation

When used with Java 7, Porphyry returns errors message such as java.lang.RuntimeException: java.lang.NullPointerException
Those messages occurs namely when the user tries to connect to a (Dolomite) password-protected Cassandre server.

When the console is open, a complementary message gives :
CacheEntry : updateAvailable=false,lastModified=Wed Nov 25 11:12:25 CET 2009,length=-1

as

easily as in an outliner.

Prerequisite: #42.

• Scénarios (Fangxu)
• Maquettes
• Tests automatisés
• Implémentation

I think you will need to clear the cache in HTTP PUT/POST/DELETE methods.

For example, when you issued a PUT request to modify a viewpoint on CouchDB, then you try to get this viewpoint immediately, you still will get the old data from cache if your listener cannot get the notification from CouchDB in time.

• Scénarios (Fangxu)
• Maquettes (Yuanjia)
• Tests automatisés
• Implémentation

Phase 1

• Scenarios (Gherkin)
• Mockups
• Implementation strategy

Phase 2

• Acceptance tests (Capybara)
• Implementation

To comply with Apple Look and Feel, launching Porphyry when it is already on, should not start another instance but use the first one instead.

N.B. This was already done in Porphyry v5. However this can be done more easily with Java 6 API (javax.jnlp.ServiceManager, SingleInstanceListener, and SingleInstanceService).

Everything in Porphyry should be referencable from a text editor, a diagram editor or a mindmapping tool with a URL of this kind:
http://acme.org/.jnlp?service=h1&service=h2&corpus=A&corpus=B&viewpoint=C&viewpoint=D&topic=a&topic=b

Description

What is the valuable outcome that cannot be achieved with current features?

For which stakeholder (people, role, project, domain) is it important?

Which user action should be enabled (or restricted)? For who?

Prerequisite: being logged in.

Additional details (solutions you think about, or workarounds you tried)

Deliverables status

Phase 1

• Scenarios (Gherkin)
• Mockups
• Implementation strategy

Phase 2

• Acceptance tests (Capybara)
• Implementation

Phase 3

• Screencast

If you realize too late that you shouldn't have upgraded to Java 7, there is a way to re-enable Java 6 without reinstalling it from scratch:
http://support.apple.com/kb/HT5559

• Scénarios (Meng)
• Maquettes (David Lorraine Yuanjia)
• Tests automatisés(Meng)
• Implémentation (Lorraine)

• Scénarios
• Maquettes
• Tests automatisés
• Implémentation

with discussion threads, links to sources, and maybe uploaded documents.

While a bit too much "post-modern" for science, comments could be "liked" by peers.

Comments could also be shared optionally on social networks to get visibility on one's work. This would also benefit the platform by dragging in additional contributors.

As an example of APIs that could be developed or integrated, here are:

• Facebook's social plugin,
• Disqus comment plugin.

This feature was already implemented in v5.

This feature existed in Porphyry v5.

Prerequisite: #35.

Similar to what was implemented on Porphyry v5 for viewpoints.

Description

What is the valuable outcome that cannot be achieved with current features?

For which stakeholder (people, role, project, domain) is it important?

Which user action should be enabled (or restricted)? For who?

Additional details (solutions you think about, or workarounds you tried)

Deliverables status

Phase 1

• Scenarios (Gherkin)
• Mockups
• Implementation strategy

Phase 2

• Acceptance tests (Capybara)
• Implementation

Phase 3

• Screencast

This feature existed in Porphyry v5.

Since Java 7 update 51, self-signed applications are blocked by default.

Unfortunately academic certificates (CNRS) are not valid for Java. Moreover we cannot afford a 150$ yearly fee to a commercial trusted third party.

A workaround is to modify your java settings so that our download server is a trusted server.

Two unexpected results have been reported:

• an empty list,
• a single concatenated name.

Description

What is the valuable outcome that cannot be achieved with current features?

For which stakeholder (people, role, project, domain) is it important?

Which user action should be enabled (or restricted)? For who?

Additional details (solutions you think about, or workarounds you tried)

Deliverables status

Phase 1

• Scenarios (Gherkin)
• Mockups
• Implementation strategy

Phase 2

• Acceptance tests (Capybara)
• Implementation

Phase 3

• Screencast

... i.e. without the META key (as in a checkbox field).

Similarly to what is done on topics, you could click on an attribute value and open the portfolio page in which every item with this value would be selected (#158) or sorted (#38) (the designers should choose either of the prerequisites).

Phase 1

• Scenarios (Gherkin)
• Mockups
• Implementation strategy

Phase 2

• Acceptance tests (Capybara)
• Implementation

... with selecting and displaying/counting of attributes values.

This feature already was in v5.

The simple cache policy in RESTDatabase – caching only successful requests – together with a "lazy object mapping" strategy in HypertopicMap causes faulty resources to be requested on HTTP again and again.

For now, using Cassandre BEFORE Argos is broken.