Rated 2 Stars (out of 5) - I can confirm the presence of an installation problem with Windows 8 Enterprise, and Excel 2013. My rating is based on the failure to install and nothing more.
↧
Reviewed: NodeXL Excel Template, version 1.0.1.245 (Aug 13, 2013)
↧
New Post: uninstall current version, install 1.0.1.113 for use with textbook
I'm going to use the text "Analyzing Social Media Networks ..." in my class in the fall. The text recommends installing NodeXL_1.0.1.113. How do I uninstall the version I currently have installed? Or is it possible for the same user to have two versions running?
↧
↧
New Post: uninstall current version, install 1.0.1.113 for use with textbook
Hello!
While using the version described in the book is sensible, I suggest that you consider using the latest version despite the significant differences between the book (v.113) and the current state of the project (v.245).
First, several features now longer work in v.113, particularly those related to data access to social media network sources (like Twitter). These services have changed their interfaces significantly over the years and we have kept up with them in updated releases. But the older versions no longer work against the current APIs.
Second, improvements and added features make using NodeXL easier now than it was in v.113. Consider the use of features like NodeXL Options files (which allow a single best set of settings to be shared among all students), which may motivate you to adopt the latest versions.
Third, significant documentation for later features are available in the help files and on my blog at http://connectedaction.net
While using the version described in the book is sensible, I suggest that you consider using the latest version despite the significant differences between the book (v.113) and the current state of the project (v.245).
First, several features now longer work in v.113, particularly those related to data access to social media network sources (like Twitter). These services have changed their interfaces significantly over the years and we have kept up with them in updated releases. But the older versions no longer work against the current APIs.
Second, improvements and added features make using NodeXL easier now than it was in v.113. Consider the use of features like NodeXL Options files (which allow a single best set of settings to be shared among all students), which may motivate you to adopt the latest versions.
Third, significant documentation for later features are available in the help files and on my blog at http://connectedaction.net
Regards,
Marc↧
New Post: uninstall current version, install 1.0.1.113 for use with textbook
It's not possible to have two versions running on the same computer.
If you already have a later version installed, either keep using it or upgrade to the latest version, as Marc suggested.
You do not have to uninstall an older version before you install a newer version. That will happen automatically.
-- Tony
If you already have a later version installed, either keep using it or upgrade to the latest version, as Marc suggested.
You do not have to uninstall an older version before you install a newer version. That will happen automatically.
-- Tony
↧
New Post: uninstall current version, install 1.0.1.113 for use with textbook
But if you do want to install the older version, I think you will need to uninstall the current version and then install the older v.113 version.
-- Marc
-- Marc
↧
↧
Commented Unassigned: Version 248 crashes when ordering vertices [24618]
Hi,
Excel crashes every time I try to order the vertices by betweeness centrality or any other measure (say, from largest to smallest). I am using version .248. Anyone else having this problem?
The workbook I was using was rather large, but the older version of NodeXL was still able to handle it with ease, if albeit a bit slowly. So I don't know what is up here.
I should also note that I am using one of the recipes from the gallery.
Thanks!
Comments: ** Comment from web user: tcap479 **
Excel crashes every time I try to order the vertices by betweeness centrality or any other measure (say, from largest to smallest). I am using version .248. Anyone else having this problem?
The workbook I was using was rather large, but the older version of NodeXL was still able to handle it with ease, if albeit a bit slowly. So I don't know what is up here.
I should also note that I am using one of the recipes from the gallery.
Thanks!
Comments: ** Comment from web user: tcap479 **
Nothing has changed recently in NodeXL that would affect column sorting, and sorting is something that is done directly by Excel anyway, so I don't think version differences can explain the problem you're seeing.
A few questions:
1. How many rows are there in the worksheet you're trying to sort?
2. How are you sorting the column? There are several ways to do that in Excel--are you just clicking the down-arrow in the column header and selecting a "Sort..." item from the menu that pops up?
3. When it crashes, do you get any kind of error message?
-- Tony
↧
New Post: uninstall current version, install 1.0.1.113 for use with textbook
Thank you for all responses. I will go with the later version (245), but it would still be useful to know how to uninstall the current version if I'd like to install an older one.
↧
New Post: uninstall current version, install 1.0.1.113 for use with textbook
That's correct.
If you go backward--from version 148 to 113, for example--then you need to manually uninstall 148 first.
If you go forward--from 113 to 148, for example--then you do not need to manually uninstall 113 first. Installing 148 will automatically replace 113.
-- Tony
If you go backward--from version 148 to 113, for example--then you need to manually uninstall 148 first.
If you go forward--from 113 to 148, for example--then you do not need to manually uninstall 113 first. Installing 148 will automatically replace 113.
-- Tony
↧
New Post: uninstall current version, install 1.0.1.113 for use with textbook
OK, I just go through the control panel. Thank you, I'm all set.
↧
↧
New Post: How to associate many archives imported from twitter (relationship users) and make a only graph ?
Hi,
I´m doing a research about online social networks, and i have a question about the NodeXL tool:
How to associate many archives imported from twitter (relationship users) and make a only graph ?
I´m doing a research about online social networks, and i have a question about the NodeXL tool:
How to associate many archives imported from twitter (relationship users) and make a only graph ?
↧
Updated Wiki: CompleteReleaseHistory
Complete NodeXL Release History
1.0.1.249 (In progress)- If your workbook had a file name that contained certain non-English characters (Korean characters, for example) and you attempted to export the workbook via NodeXL, Data, Export, To Email, you would get a message saying "A problem occurred while sending the email."
1.0.1.248 (2013-08-09)
- If you import a network from the NodeXL Graph Server, the graph summary (NodeXL, Graph, Summary) now includes more information, including the date range of the tweets in the network.
- The Data Import section of the Graph Summary for all Twitter, YouTube and Flickr network is now broken into paragraphs for clarity.
- When it looks for user names in tweets, NodeXL now ignores most punctuation. For example, the user name "john" in the tweet "Hello,@john" wasn't being detected, because it was preceded by a comma instead of a space.
- NodeXL will now pause for an extra 15 seconds when Twitter rate limits are reached. This is an attempt to work around a problem where Twitter occasionally refuses to provide more information even after NodeXL pauses for the time specified by Twitter. The symptom of that problem is a message that includes the text "A likely cause is that you have made too many Twitter requests in the last 15 minutes." (This might not fix the problem, the cause of which is unknown.)
1.0.1.247 (2013-08-02)
- If you import a Twitter search network and tell NodeXL to calculate Twitter search network top items (NodeXL, Analysis, Graph Metrics), then the following columns now get added to the Vertices worksheet: Top URLs in Tweet by Count, Top URLs in Tweet by Salience, Top Domains in Tweet by Count, Top Domains in Tweet by Salience, Top Hashtags in Tweet by Count, Top Hashtags in Tweet by Salience, Top Words in Tweet by Count, Top Words in Tweet by Salience, Top Word Pairs in Tweet by Count, Top Word Pairs in Tweet by Salience.
- When importing a Twitter network, if Twitter unexpectedly closes the network connection, then NodeXL will now try to reestablish the connection. (The symptom of this problem is a message that includes the text "[IOException]: Unable to read data from the transport connection: The connection was closed.")
1.0.1.246 (2013-07-19)
- An importer for a new Graph Server has been added. The Graph Server is currently private.
- Bug fix: If you used NodeXL, Analysis, Subgraph Images and one of your vertices had a name that was "reserved" by Windows (con, lpt, nul, and several others), you would get an error message that included the text "[ExternalException]: A generic error occurred in GDI+". Note that subgraph image file names now always start with "Img-", as in "Img-con.png".
1.0.1.245 (2013-06-19)
- This release wraps up a set of enhancements and bug fixes that were previously included in a series of experimental private releases. All changes since the last public release (1.0.1.238) have to do with importing Twitter networks.
- An experiment involving "shared term" edges in the Twitter search network is still in progress, and those edges are not included in this release. (They were not included in version 1.0.1.244, either.)
- This release is functionally identical to version 1.0.1.244.
1.0.1.244 (2013-06-17, private release)
- In the Twitter search network, vertices are now added to the graph for people who were replied to or mentioned by the people who actually tweeted the specified term.
- Bug fix: In the Twitter networks, if you checked "Expand URLs in tweets" and a malformed URL was provided by Twitter, you would get a "Partial Network" message and then the graph would have no edges. The Partial Network details included the text "[UriFormatException]: Invalid URI: The format of the URI could not be determined". Now, NodeXL doesn't attempt to expand the bad URL.
- Bug fix: When getting a Twitter search network, you would sometimes get a "Partial Network" message with details that included the text "[KeyNotFoundException]: The given key was not present in the dictionary." (This was caused by Twitter giving NodeXL a tweet that included no information about the tweeter. NodeXL now ignores such tweets.)
1.0.1.243 (2013-05-19, private release)
- The Twitter Search Network now uses experimental shared term thresholds. This is part of an effort to obtain meaningful edges without running into Twitter's new rate limits.
1.0.1.242 (2013-05-01, private release)
- The shared word user threshold can now be specified in the network configuration file used by the Network Server program. (For advanced users of private releases only.)
- Bug fix: If you specified shared hashtag, URL, word, or word pair edge relationships in the Import from Twitter Search Network dialog box, the graph summary (NodeXL, Graph, Summary) did not mention the fact that the graph included those edges. (Private releases only.)
1.0.1.241 (2013-04-25, private release)
- Bug fix: If you imported a Twitter network that included the empty hyperlink "http://" somewhere in the network's text, Excel would refuse to save the workbook. The error message started with "Errors were detected while saving..." This is an Excel bug that will also arise if you type "http://" directly into a cell. This change does not fix the latter problem.
1.0.1.240 (2013-04-24, private release)
- If you check "add statistic columns to the Vertices worksheet" in the Import from Twitter Search Network dialog box, no additional time will be required to get the network. This used to require additional Twitter requests, and it was marked as "slower" in the dialog box.
1.0.1.239 (2013-04-08, private release)
- Same as 1.0.1.238, but with additional edge options.
1.0.1.238 (2013-04-08)
- Bug fix: In versions 1.0.1.236 and 237, if you entered a space (or a colon, or a few other special characters) into the "Add a vertex for each..." textbox on the Import from Twitter Search Network dialog box, you would get a message that included the text, "The Twitter Web service refused to provide the requested information."
1.0.1.237 (2013-03-25, private release)
- Same as 1.0.1.236, but with additional edge options.
1.0.1.236 (2013-03-25)
- There are some major changes in NodeXL's Twitter importers. See Changes in NodeXL's Twitter Importers for more information.
- When you use dynamic filters (NodeXL, Analysis, Dynamic Filters), filtering an edge will automatically filter its adjacent vertices if the filtering causes those vertices to become isolates.
- If you set the Visibility of vertex X to "Skip" and vertex X has adjacent vertices that are connected only to vertex X, then those adjacent vertices are now skipped as well. Previously, the adjacent vertices would remain in the graph as isolates.
- For programmers: The NodeXL source code is now available on the CodePlex "Source Code" tab. The source code will no longer be provided as separate releases on the Downloads tab.
↧
Updated Wiki: CompleteReleaseHistory
Complete NodeXL Release History
1.0.1.249 (In progress)- Bug fix: If your workbook had a file name that contained certain non-English characters (Korean characters, for example) and you attempted to export the workbook via NodeXL, Data, Export, To Email, you would get a message saying "A problem occurred while sending the email."
1.0.1.248 (2013-08-09)
- If you import a network from the NodeXL Graph Server, the graph summary (NodeXL, Graph, Summary) now includes more information, including the date range of the tweets in the network.
- The Data Import section of the Graph Summary for all Twitter, YouTube and Flickr network is now broken into paragraphs for clarity.
- When it looks for user names in tweets, NodeXL now ignores most punctuation. For example, the user name "john" in the tweet "Hello,@john" wasn't being detected, because it was preceded by a comma instead of a space.
- NodeXL will now pause for an extra 15 seconds when Twitter rate limits are reached. This is an attempt to work around a problem where Twitter occasionally refuses to provide more information even after NodeXL pauses for the time specified by Twitter. The symptom of that problem is a message that includes the text "A likely cause is that you have made too many Twitter requests in the last 15 minutes." (This might not fix the problem, the cause of which is unknown.)
1.0.1.247 (2013-08-02)
- If you import a Twitter search network and tell NodeXL to calculate Twitter search network top items (NodeXL, Analysis, Graph Metrics), then the following columns now get added to the Vertices worksheet: Top URLs in Tweet by Count, Top URLs in Tweet by Salience, Top Domains in Tweet by Count, Top Domains in Tweet by Salience, Top Hashtags in Tweet by Count, Top Hashtags in Tweet by Salience, Top Words in Tweet by Count, Top Words in Tweet by Salience, Top Word Pairs in Tweet by Count, Top Word Pairs in Tweet by Salience.
- When importing a Twitter network, if Twitter unexpectedly closes the network connection, then NodeXL will now try to reestablish the connection. (The symptom of this problem is a message that includes the text "[IOException]: Unable to read data from the transport connection: The connection was closed.")
1.0.1.246 (2013-07-19)
- An importer for a new Graph Server has been added. The Graph Server is currently private.
- Bug fix: If you used NodeXL, Analysis, Subgraph Images and one of your vertices had a name that was "reserved" by Windows (con, lpt, nul, and several others), you would get an error message that included the text "[ExternalException]: A generic error occurred in GDI+". Note that subgraph image file names now always start with "Img-", as in "Img-con.png".
1.0.1.245 (2013-06-19)
- This release wraps up a set of enhancements and bug fixes that were previously included in a series of experimental private releases. All changes since the last public release (1.0.1.238) have to do with importing Twitter networks.
- An experiment involving "shared term" edges in the Twitter search network is still in progress, and those edges are not included in this release. (They were not included in version 1.0.1.244, either.)
- This release is functionally identical to version 1.0.1.244.
1.0.1.244 (2013-06-17, private release)
- In the Twitter search network, vertices are now added to the graph for people who were replied to or mentioned by the people who actually tweeted the specified term.
- Bug fix: In the Twitter networks, if you checked "Expand URLs in tweets" and a malformed URL was provided by Twitter, you would get a "Partial Network" message and then the graph would have no edges. The Partial Network details included the text "[UriFormatException]: Invalid URI: The format of the URI could not be determined". Now, NodeXL doesn't attempt to expand the bad URL.
- Bug fix: When getting a Twitter search network, you would sometimes get a "Partial Network" message with details that included the text "[KeyNotFoundException]: The given key was not present in the dictionary." (This was caused by Twitter giving NodeXL a tweet that included no information about the tweeter. NodeXL now ignores such tweets.)
1.0.1.243 (2013-05-19, private release)
- The Twitter Search Network now uses experimental shared term thresholds. This is part of an effort to obtain meaningful edges without running into Twitter's new rate limits.
1.0.1.242 (2013-05-01, private release)
- The shared word user threshold can now be specified in the network configuration file used by the Network Server program. (For advanced users of private releases only.)
- Bug fix: If you specified shared hashtag, URL, word, or word pair edge relationships in the Import from Twitter Search Network dialog box, the graph summary (NodeXL, Graph, Summary) did not mention the fact that the graph included those edges. (Private releases only.)
1.0.1.241 (2013-04-25, private release)
- Bug fix: If you imported a Twitter network that included the empty hyperlink "http://" somewhere in the network's text, Excel would refuse to save the workbook. The error message started with "Errors were detected while saving..." This is an Excel bug that will also arise if you type "http://" directly into a cell. This change does not fix the latter problem.
1.0.1.240 (2013-04-24, private release)
- If you check "add statistic columns to the Vertices worksheet" in the Import from Twitter Search Network dialog box, no additional time will be required to get the network. This used to require additional Twitter requests, and it was marked as "slower" in the dialog box.
1.0.1.239 (2013-04-08, private release)
- Same as 1.0.1.238, but with additional edge options.
1.0.1.238 (2013-04-08)
- Bug fix: In versions 1.0.1.236 and 237, if you entered a space (or a colon, or a few other special characters) into the "Add a vertex for each..." textbox on the Import from Twitter Search Network dialog box, you would get a message that included the text, "The Twitter Web service refused to provide the requested information."
1.0.1.237 (2013-03-25, private release)
- Same as 1.0.1.236, but with additional edge options.
1.0.1.236 (2013-03-25)
- There are some major changes in NodeXL's Twitter importers. See Changes in NodeXL's Twitter Importers for more information.
- When you use dynamic filters (NodeXL, Analysis, Dynamic Filters), filtering an edge will automatically filter its adjacent vertices if the filtering causes those vertices to become isolates.
- If you set the Visibility of vertex X to "Skip" and vertex X has adjacent vertices that are connected only to vertex X, then those adjacent vertices are now skipped as well. Previously, the adjacent vertices would remain in the graph as isolates.
- For programmers: The NodeXL source code is now available on the CodePlex "Source Code" tab. The source code will no longer be provided as separate releases on the Downloads tab.
↧
Updated Wiki: CompleteReleaseHistory
Complete NodeXL Release History
1.0.1.249 (2013-08-14)- Bug fix: If your workbook had a file name that contained certain non-English characters (Korean characters, for example) and you attempted to export the workbook via NodeXL, Data, Export, To Email, you would get a message saying "A problem occurred while sending the email."
1.0.1.248 (2013-08-09)
- If you import a network from the NodeXL Graph Server, the graph summary (NodeXL, Graph, Summary) now includes more information, including the date range of the tweets in the network.
- The Data Import section of the Graph Summary for all Twitter, YouTube and Flickr network is now broken into paragraphs for clarity.
- When it looks for user names in tweets, NodeXL now ignores most punctuation. For example, the user name "john" in the tweet "Hello,@john" wasn't being detected, because it was preceded by a comma instead of a space.
- NodeXL will now pause for an extra 15 seconds when Twitter rate limits are reached. This is an attempt to work around a problem where Twitter occasionally refuses to provide more information even after NodeXL pauses for the time specified by Twitter. The symptom of that problem is a message that includes the text "A likely cause is that you have made too many Twitter requests in the last 15 minutes." (This might not fix the problem, the cause of which is unknown.)
1.0.1.247 (2013-08-02)
- If you import a Twitter search network and tell NodeXL to calculate Twitter search network top items (NodeXL, Analysis, Graph Metrics), then the following columns now get added to the Vertices worksheet: Top URLs in Tweet by Count, Top URLs in Tweet by Salience, Top Domains in Tweet by Count, Top Domains in Tweet by Salience, Top Hashtags in Tweet by Count, Top Hashtags in Tweet by Salience, Top Words in Tweet by Count, Top Words in Tweet by Salience, Top Word Pairs in Tweet by Count, Top Word Pairs in Tweet by Salience.
- When importing a Twitter network, if Twitter unexpectedly closes the network connection, then NodeXL will now try to reestablish the connection. (The symptom of this problem is a message that includes the text "[IOException]: Unable to read data from the transport connection: The connection was closed.")
1.0.1.246 (2013-07-19)
- An importer for a new Graph Server has been added. The Graph Server is currently private.
- Bug fix: If you used NodeXL, Analysis, Subgraph Images and one of your vertices had a name that was "reserved" by Windows (con, lpt, nul, and several others), you would get an error message that included the text "[ExternalException]: A generic error occurred in GDI+". Note that subgraph image file names now always start with "Img-", as in "Img-con.png".
1.0.1.245 (2013-06-19)
- This release wraps up a set of enhancements and bug fixes that were previously included in a series of experimental private releases. All changes since the last public release (1.0.1.238) have to do with importing Twitter networks.
- An experiment involving "shared term" edges in the Twitter search network is still in progress, and those edges are not included in this release. (They were not included in version 1.0.1.244, either.)
- This release is functionally identical to version 1.0.1.244.
1.0.1.244 (2013-06-17, private release)
- In the Twitter search network, vertices are now added to the graph for people who were replied to or mentioned by the people who actually tweeted the specified term.
- Bug fix: In the Twitter networks, if you checked "Expand URLs in tweets" and a malformed URL was provided by Twitter, you would get a "Partial Network" message and then the graph would have no edges. The Partial Network details included the text "[UriFormatException]: Invalid URI: The format of the URI could not be determined". Now, NodeXL doesn't attempt to expand the bad URL.
- Bug fix: When getting a Twitter search network, you would sometimes get a "Partial Network" message with details that included the text "[KeyNotFoundException]: The given key was not present in the dictionary." (This was caused by Twitter giving NodeXL a tweet that included no information about the tweeter. NodeXL now ignores such tweets.)
1.0.1.243 (2013-05-19, private release)
- The Twitter Search Network now uses experimental shared term thresholds. This is part of an effort to obtain meaningful edges without running into Twitter's new rate limits.
1.0.1.242 (2013-05-01, private release)
- The shared word user threshold can now be specified in the network configuration file used by the Network Server program. (For advanced users of private releases only.)
- Bug fix: If you specified shared hashtag, URL, word, or word pair edge relationships in the Import from Twitter Search Network dialog box, the graph summary (NodeXL, Graph, Summary) did not mention the fact that the graph included those edges. (Private releases only.)
1.0.1.241 (2013-04-25, private release)
- Bug fix: If you imported a Twitter network that included the empty hyperlink "http://" somewhere in the network's text, Excel would refuse to save the workbook. The error message started with "Errors were detected while saving..." This is an Excel bug that will also arise if you type "http://" directly into a cell. This change does not fix the latter problem.
1.0.1.240 (2013-04-24, private release)
- If you check "add statistic columns to the Vertices worksheet" in the Import from Twitter Search Network dialog box, no additional time will be required to get the network. This used to require additional Twitter requests, and it was marked as "slower" in the dialog box.
1.0.1.239 (2013-04-08, private release)
- Same as 1.0.1.238, but with additional edge options.
1.0.1.238 (2013-04-08)
- Bug fix: In versions 1.0.1.236 and 237, if you entered a space (or a colon, or a few other special characters) into the "Add a vertex for each..." textbox on the Import from Twitter Search Network dialog box, you would get a message that included the text, "The Twitter Web service refused to provide the requested information."
1.0.1.237 (2013-03-25, private release)
- Same as 1.0.1.236, but with additional edge options.
1.0.1.236 (2013-03-25)
- There are some major changes in NodeXL's Twitter importers. See Changes in NodeXL's Twitter Importers for more information.
- When you use dynamic filters (NodeXL, Analysis, Dynamic Filters), filtering an edge will automatically filter its adjacent vertices if the filtering causes those vertices to become isolates.
- If you set the Visibility of vertex X to "Skip" and vertex X has adjacent vertices that are connected only to vertex X, then those adjacent vertices are now skipped as well. Previously, the adjacent vertices would remain in the graph as isolates.
- For programmers: The NodeXL source code is now available on the CodePlex "Source Code" tab. The source code will no longer be provided as separate releases on the Downloads tab.
↧
↧
Source code checked in, #72833
Working on version 1.0.1.249.
↧
Source code checked in, #72834
Updates the NodeXL source code to version 1.0.1.249.
↧
Released: NodeXL Excel Template, version 1.0.1.249 (Aug 14, 2013)
The NodeXL Excel template displays a network graph using edge and vertex lists stored in an Excel 2007 or Excel 2010 workbook.
Please help support the development of NodeXL with your donation.
Installing for multiple users: There is an option in the setup program to install for "Just Me" or "Everyone." Most people should accept the default "Just Me" option. If you think you need the "Everyone" option, please see How to install NodeXL for multiple users for more information.
Please help support the development of NodeXL with your donation.
What's New
This release fixes a bug involving non-English characters in file names. See the Complete NodeXL Release History for more information.Installation Steps
Follow these steps to install and use the template:- Download the Zip file.
- Unzip it into any folder. Use WinZip or a similar program, or just right-click the Zip file in Windows Explorer and select "Extract All."
- Close Excel if it's open.
- Run Setup.exe. You need to be an administrator to do this. (You don't need to be an administrator to actually use the NodeXL template once it's installed, however.) The setup program might install some Microsoft prerequisites. These are the Microsoft. .NET Framework 3.5 Service Pack 1, the Microsoft Office 2007 Primary Interop Assemblies, and the Microsoft Visual Studio Tools for the Office System 3.0 Runtime Service Pack 1.
- Delete the unzipped files. They're no longer needed.
- Register. If you didn't register while running Setup.exe, please do so here. Registration is optional.
- Use the template. In the Windows Start menu, click "All Programs" (Windows 7 or Vista) or "Programs" (XP), then "NodeXL," then "Excel Template."
Installing for multiple users: There is an option in the setup program to install for "Just Me" or "Everyone." Most people should accept the default "Just Me" option. If you think you need the "Everyone" option, please see How to install NodeXL for multiple users for more information.
System Requirements
- Windows 7, Vista, or XP. (Will also work within Parallels Desktop and VMware Fusion on the Mac.)
- Office 2007 or 2010.
- NodeXL has not been tested yet with Office 2013 or Windows 8.
Release History
Please see the Complete NodeXL Release History.↧
Updated Release: NodeXL Excel Template, version 1.0.1.249 (Aug 14, 2013)
The NodeXL Excel template displays a network graph using edge and vertex lists stored in an Excel 2007 or Excel 2010 workbook.
Please help support the development of NodeXL with your donation.
Installing for multiple users: There is an option in the setup program to install for "Just Me" or "Everyone." Most people should accept the default "Just Me" option. If you think you need the "Everyone" option, please see How to install NodeXL for multiple users for more information.
Please help support the development of NodeXL with your donation.
What's New
This release fixes a bug involving non-English characters in file names. See the Complete NodeXL Release History for more information.Installation Steps
Follow these steps to install and use the template:- Download the Zip file.
- Unzip it into any folder. Use WinZip or a similar program, or just right-click the Zip file in Windows Explorer and select "Extract All."
- Close Excel if it's open.
- Run Setup.exe. You need to be an administrator to do this. (You don't need to be an administrator to actually use the NodeXL template once it's installed, however.) The setup program might install some Microsoft prerequisites. These are the Microsoft. .NET Framework 3.5 Service Pack 1, the Microsoft Office 2007 Primary Interop Assemblies, and the Microsoft Visual Studio Tools for the Office System 3.0 Runtime Service Pack 1.
- Delete the unzipped files. They're no longer needed.
- Register. If you didn't register while running Setup.exe, please do so here. Registration is optional.
- Use the template. In the Windows Start menu, click "All Programs" (Windows 7 or Vista) or "Programs" (XP), then "NodeXL," then "Excel Template."
Installing for multiple users: There is an option in the setup program to install for "Just Me" or "Everyone." Most people should accept the default "Just Me" option. If you think you need the "Everyone" option, please see How to install NodeXL for multiple users for more information.
System Requirements
- Windows 7, Vista, or XP. (Will also work within Parallels Desktop and VMware Fusion on the Mac.)
- Office 2007 or 2010.
- NodeXL has not been tested yet with Office 2013 or Windows 8.
Release History
Please see the Complete NodeXL Release History.↧
↧
New Post: Making a graph look neater overall
You can upload to the NodeXL Graph Gallery via the export menu.
Or attach it to an item in the issues list.
-- Marc
Sent from my iPhone
Sent from my iPhone
↧
New Post: Making a graph look neater overall
Ok I just uploaded it to the gallery. Its called Resource Management Strategies.
↧
New Post: Making a graph look neater overall
Try the circle layout and use a metric for layout order that is useful: maybe degree or another attribute value (head count, budget, etc)?
Marc
Sent from my iPhone
Sent from my iPhone
↧